Generalized from Karpathy's autoresearch. Same loop, any domain.
An AI agent runs an infinite hill-climbing loop: modify → run → measure → keep or revert → repeat. No human in the loop. Wake up to a TSV of completed experiments.
| /* | |
| * provision_device_ids.c | |
| * Copyright (c) 2026 mhmrdd. All rights reserved. | |
| * | |
| * Standalone Device ID provisioning utility for Qualcomm Keymaster. | |
| * | |
| * This tool provisions Android attestation identifiers (brand, device, | |
| * product, serial, IMEI/MEID, manufacturer, model) into secure storage | |
| * through QSEECom and finalizes Device ID provisioning state. | |
| * |
| """ | |
| The most atomic way to train and run inference for a GPT in pure, dependency-free Python. | |
| This file is the complete algorithm. | |
| Everything else is just efficiency. | |
| @karpathy | |
| """ | |
| import os # os.path.exists | |
| import math # math.log, math.exp |
| <<< System >>> | |
| Manufacturer: rainx | |
| Model: theloop | |
| Brand: rainx | |
| Board: tb8791p1_64 | |
| Device: theloop | |
| Hardware: mt6877 | |
| Platform: mt6877 | |
| Product: theloop |
Generalized from Karpathy's autoresearch. Same loop, any domain.
An AI agent runs an infinite hill-climbing loop: modify → run → measure → keep or revert → repeat. No human in the loop. Wake up to a TSV of completed experiments.
Previous tutorials didnt worked for me because my setup is a little bit odd.
I'm using windows 11 machine with WSL2 and docker desktop.
I also use k3d to create kubernetes cluster. Also my k3d cluster have local registry
I also used skaffold and other shinigens
%USERPROFILE%\AppData\Local\Docker\wsl\disk\ - there is your docker_data.vhdx
| /* | |
| * Assets内の全MaterialのShaderを一括で置換するEditor拡張 | |
| * 使い方 | |
| * 1.Editorディレクトリ配下にScriptを配置 | |
| * 2.AssetsにShaderReplaceが追加されるので、それを選択するとWindowsが開く | |
| * 3.Beforeに置換前のShader、Afterに置換後のShaderを選択 | |
| * 4.Replaceボタンを押すと全部のMaterialでShaderを置換 | |
| */ | |
| using System.Linq; |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Pony Prompt Builder</title> | |
| <link href="https://fonts.googleapis.com/css2?family=JetBrains+Mono:wght@400;500;600;700&family=Space+Grotesk:wght@400;500;600;700&display=swap" rel="stylesheet"> | |
| <style> | |
| :root{--bg-deep:#0d0d0f;--bg-panel:#16161a;--bg-card:#1e1e24;--bg-card-hover:#25252d;--bg-input:#111114;--border:#2a2a33;--border-active:#4a4a5a;--text-primary:#e8e6e3;--text-secondary:#8a8a96;--text-dim:#55555f;--accent-pos:#4fc1a6;--accent-pos-dim:#4fc1a620;--accent-neg:#e06c75;--accent-neg-dim:#e06c7520;--accent-blue:#61afef;--accent-blue-dim:#61afef20;--accent-yellow:#e5c07b;--accent-yellow-dim:#e5c07b20;--accent-purple:#c678dd;--accent-purple-dim:#c678dd20;--accent-orange:#d19a66;--accent-orange-dim:#d19a6620;--accent-cyan:#56b6c2;--accent-cyan-dim:#56b6c220;--accent-pink:#e06ca0;--accent-pink-dim:#e06ca020;--tag-quality:#c678dd;--tag-source:#61afef;--tag-rating:#e5c07b; |
| // Zed keymap | |
| // | |
| // For information on binding keys, see the Zed | |
| // documentation: https://zed.dev/docs/key-bindings | |
| // | |
| // To see the default key bindings run `zed: open default keymap` | |
| // from the command palette. | |
| [ | |
| { | |
| "context": "Workspace", |
This document provides a comprehensive guide for creating Orchestrator Agents in OpenCode. Based on the reference implementation (@agent/orchestrator.md), this guide details the structure, patterns, and best practices for building intelligent routing agents.
An Orchestrator Agent serves as a central dispatch system. Unlike standard agents that execute tasks, an orchestrator's sole purpose is to analyze user requests and delegate work to specialized subagents.
| # USBank | |
| # Major Banks | |
| # Chase | |
| DOMAIN-KEYWORD,chase | |
| DOMAIN-SUFFIX,chase.com | |
| DOMAIN-SUFFIX,jpmorganchase.com | |
| DOMAIN-SUFFIX,jpmorgan.com | |
| DOMAIN-SUFFIX,chasepaymentech.com | |
| # Bank of America |